Recovery Process

The procedure below describes the recovery process.

To run the recovery process:
1. If the primary machine fails, use the Server Manager to make sure the OVOC application has been closed, before starting the secondary machine recovery process.
2. Do not run the OVOC software on the secondary machine at this stage. Just make sure the machine is up and running.
3. Verify that server software version is the same as on the Primary server, by checking the OVOC server Manager title.
4. Start the secondary server machine, making sure that all the processes are up and running.
5. Make sure that all backup files are in the /data/NBIF directory.
6. In OVOC Server Manager, go to the Application Maintenance menu and select the Restore option (OVOC Server Restore).
7. Follow the instructions during the process; you might need to press Enter a few times.
8. After the restore operation has completed, you are prompted to reboot the OVOC server.
9. If you have installed custom certificates prior to the restore, you must re-install them.
10. Login to the OVOC Web client and verify that there is connectivity and the application is functioning correctly.
11. If you are using one or more features which are marked in the table below as ‘Not Supported’, please provision all the managed devices with a new Management Server IP address.
12. For SBC Fixed and Floating License Pool customers, run the Update command for all the managed devices .

See the table below summarizing the features affected byDisaster Recovery functionality.

Features Affected by Disaster Recovery Functionality

Feature

Status

Management

Alarms+ NAT communication based on Keepalive traps

Supported

Fixed License Pool and Floating License

Not Supported

IP Phones Manager Pro: Alarms / Status reports

Not Supported

Advanced Quality Package

-

SBC/Gateway Voice Quality Monitoring

Supported

Endpoint Quality monitoring (RFC 6035)

Not Supported

Server

Server: Device NTP Server

Supported

Server: Device Syslog Server

Not Supported

Server: Device TP Debug recording server

Not Supported